Cherry-pick #24607 to 7.x: Improve support for log_statement and log_duration in PostgreSQL module #24841
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry-pick of PR #24607 to 7.x branch. Original message:
What does this PR do?
event.dataset: postgresql.log
for better performance.Why is it important?
Checklist
I have commented my code, particularly in hard-to-understand areasI have made corresponding changes to the documentationSee Add docs about PostgreSQL monitoring #24588.I have made corresponding change to the default configuration filesCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues
Use cases
Module works better now when logs include lines generated by statements when
log_statement
is used and/orlog_min_duration_statement
is not used, giving a better initial experience in some cases, and allowing different options to configure PostgreSQL and still get relevant data.